CVE-2025-52661
HCL AION JWT Token Expiry Too Long Authentication Bypass
Description
HCL AION version 2 is affected by a JWT Token Expiry Too Long vulnerability. This may increase the risk of token misuse, potentially resulting in unauthorized access if the token is compromised.
INFO
Published Date :
Jan. 19, 2026, 6:16 p.m.
Last Modified :
Jan. 30, 2026, 4:21 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | LOW | 1e47fe04-f25f-42fa-b674-36de2c5e3cfc | ||||
| CVSS 3.1 | LOW | [email protected] | ||||
| CVSS 3.1 | LOW | MITRE-CVE | ||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Configure JWT token expiry to a shorter duration.
- Implement strict token validation checks.
- Monitor token usage for suspicious activity.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-52661.
| URL | Resource |
|---|---|
| https://support.hcl-software.com/kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995# | Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-52661 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-52661
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-52661 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-52661 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jan. 30, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Added CPE Configuration OR *cpe:2.3:a:hcltech:aion:2.0:*:*:*:*:*:*:* Added Reference Type HCL Software: https://support.hcl-software.com/kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995# Types: Vendor Advisory -
New CVE Received by [email protected]
Jan. 19, 2026
Action Type Old Value New Value Added Description HCL AION version 2 is affected by a JWT Token Expiry Too Long vulnerability. This may increase the risk of token misuse, potentially resulting in unauthorized access if the token is compromised. Added CVSS V3.1 AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N Added CWE CWE-613 Added Reference https://support.hcl-software.com/kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995#